Release 10.1A: OpenEdge Development:
Java Open Clients

Developing and deploying a SmartDataObject-aware application

To develop and deploy Java applications that access SmartDataObjects:

Use the AppBuilder to create and compile a SmartDataObject.
Deploy the compiled SmartDataObject (the *.r file) on the AppServer side. (The compiled SmartDataObject must be on the PROPATH of the AppServer.)
Copy the OpenEdge-compiled ADM2 (Application Development Model, Version 2) r-code files to a directory in the AppServer PROPATH. You can find these files in the OpenEdge-install-directory\gui\adm2 directory, wherever you have the OpenEdge AppBuilder installed. To complete this step, copy these files to your AppServer’s OpenEdge-install-directory\tty\adm2\ directory.
Deploy the Open Client Runtime package on the client side. For more information, see Chapter 1, " Configuring and Deploying Java Open Client Applications."
If your Java application needs only SmartDataObject access—it does not access other remote 4GL procedures—you are ready to write Java applications that access the SmartDataObject.

If your Java application needs to access 4GL procedures other than SmartDataObjects, use ProxyGen to create the proxies and deploy them on the client side (see OpenEdge Development: Open Client Introduction and Programming ). You do not have to map the SmartDataObject as a ProcObject, however; ProxyGen provides built-in access to SmartDataObjects in Java.

Extending a SmartDataObject

If you extend (add new 4GL methods to) a SmartDataObject, to access these extensions you must access the SmartDataObject as a separate ProcObject you create in ProxyGen. This allows you to directly access the SmartDataObject as a Progress persistent procedure with complete access to its public internal procedures and user-defined functions. For more information on accessing a SmartDataObject as a ProcObject, see OpenEdge Development: Open Client Introduction and Programming .